This page last changed on Jan 19, 2007 by kgomes.

Weekly Meeting Agenda

Updates Around The Table

Mike M

  1. New HOOVES/RCP
    • Struggling, but progress.
    • org.mbari.hooves in own CVS project "hooves"
    • Data binding framework that allowed model object to be used in forms. Adding listener support for property changes.
    • So overall, RCP is going well.
    • HOOVES will be on hold for a bit for M0 data.
  2. DTS Job to copy data from old architecture to new.
    • Asking Neil to port that to a DTC job on Fog (Kevin needs to follow up with Neil, DTS jobs broken)
      • Look in master script for server polyp.
  3. M0 data request/more data processing
    • Will be impacted by meeting tomorrow.
    • Request is to access data from anytime period.
    • These are the post processed data sets.
    • Will meet with Reiko
    • Needs Andrew's work on the auto Perl module and will bite the bullet and go with new architecture.
    • Told John R about a week.
    • Notifications are enabled by listener properties, but does not address remote clients.
    • This could be based on a message bus architecture. dev.java.net project called event bus.

Andrew

  1. ACE update
    • Kent and Tom and list of to dos and pretty much done. Waiting on them. Still issue with tracking jars and how to deal with them. Not currently working on it.
  2. XML Editor
    • Fallen by the wayside. Needing time to work on. Pick back up after architecture roll out.
  3. Caress data
    • Half way finished, will finish on contingency time. Will do after perl module.
    • Front end is done, Google maps with our bathymetry. Will need to sit down and go over to make sure it can extend.
  4. ANTLR
    • General parser that gives SSDS code parse tree. Then generate perl modules. Moving into the SSDS code base. Other languages will probably be fairly straightforward.
  5. Benthic Rover Data Management
    • In conception right now.
    • Data should be showing up in mid 2006.

John

  1. M1 Turnaround status
    • Waiting on the new architecture before changing.
    • M0 puck needs to be reburned.
  2. We need to check to see if Paul has already re-burned the PUCK (yes, they have)
    • Tomorrows meeting:
    • Meet with John at 8:00 tomorrow.
  3. JSF/Web app flow (This is back to John)
    • Mike SWT components should be able to be exported to web pages.
    • Getting up and running on development environment, then focus on JSF.
  4. Documentation Status
    • Nothing but with JSF discussion
  5. NSF Proposal (likely to pull John off SSDS till February)
    • Not going forward, John back on SSDS.

Luis

  1. MMI status
    • Finished final workshop report.
    • SSDS problems with services (no progess).

Mike G

  1. ASAP Data Systems Update

Kevin

  1. SSDS Hours/Project Plan update
    • 2005
      • 320 allocated for core and we were 43 days over, if you adjust out 60 days MMI time, we were under by 17.
      • As a project we were over by 87 days (billable to SSDS)), if you adjust out 60 days MMI time, we were over by 27.
        • Kevin (144 allocated, spent 156: 12+)
        • John (90 allocated, spent 114: 24+) This is not correct, 60 days went against MMI
        • Andrew (82 allocated, spent 93: 11+)
        • Mike (36 days)
        • Nancy Barr (3 days)
        • Rich (3 days)
        • Dorothy (13 days)
        • Karen (4 days)
      • 2006 Allocations
        • Kevin: 126 days
        • John: 40 days <b><i>(is this correct?)</i></b>
        • Andrew: 20 days
  2. Need project schedule for 2006(this week)
  3. Development
    • General
      • New machine order HP dual athalon with Red Hat
        • Need to draft up deployment and migration scenario for new architecture/new machine
      • Web Application
      • Core Metadata
      • Core Data
      • Clients
      • Model Integration
  4. MSE
      • Need to document requirements for data access (by tomorrow!)
      • No update on data policy
  5. ASAP
      • Need to meet with Mike G to discuss schema changes.

Action Items

  1. Getting new architecture rolled out is critical (time wise)
  2. Finish up DTS job migration
  3. Get project plan done and identify tasks for developers
  4. Look at eventbus: as possible solution for remote model object notificaton (and other SSDS stuff).
  5. Finish getting John's development environment going
  6. Get ASAP update from Mike G.
Document generated by Confluence on Feb 04, 2026 08:56